This is great! I'll review this and let you know.

Happy to help! Just want to say that I started with the official MySql.EntityFrameworkCore package, but ran into problems within the EntityFrameworkRelationalDatabaseConnection something wrong with the package where it casts longs to ints. So I switched to Pomelo.EntityFrameworkCore.MySql. Still supported nevertheless.

Turns out the Pomelo.EntityFrameworkCore.MySql package is compatible with MariaDB as well. I made a demo branch to test it out. Just needed to add some frontend code, and that was it. I bet we can do the same with Azure Database using MS SQL Server.

So maybe Pemelo is the way to go?

@SimonNyvall I totally agree, Pomelo is the way to go. Supporting MariaDB as well is an awesome bonus. I'll be reviewing this PR in the next few hours and I'll send you any feedback. Thank you for all the hard work here!

I've never messed with Azure SQL DB but if we can add support for it as well using the same MS SQL Server driver that would be wonderful. I wonder if #66 will be a part of implementing that.

Looks good! It's ready to merge. I looked at the demo branch for MariaDB looks like you got a handle on things there too. I'll merge this PR and you can submit the MariaDB changes when you're ready.

I found a nuget package reference conflict but that is an issue that isn't directly related to the changes you made, your changes surfaced the issue though. I'll solve it after merging this.

No worries, I thought it was fun. Like I said, happy to help!

I have been taking a deeper look into the mariaDb support without adding duplicate code to the backend and there seems to be a few issues with that strategy (works but not the finesses). Have a free day tomorrow, so I will se what I can do.

Checked out issue #66 and I can try to replicate the problem and a fix after I have finished the maria support. I guess those are similar, and that we need to implement a separate instance of mariaDb and Azure SQL that is separate from mySQL and SQL Server.